Application control interworking in network

ABSTRACT

Various communication systems may benefit from application control interworking in a network to expose certain service capabilities. For example, certain communication systems of the third generation partnership project (3GPP) that provide service capabilities that are exposed to application providers, for example, via open mobile alliance-application programming interface, may benefit from application control interworking in a network. Further, an application programming interface and the 3GPP system can act together to expose 3GPP service capabilities. A method may include receiving parameters of capabilities relating to an application server at a policy and charging rules function. The method may also include creating application detection and control rules based on the parameters received.

BACKGROUND Field

Various communication systems may benefit from application controlinterworking in a network to expose certain service capabilities. Forexample, certain communication systems of the third generationpartnership project (3GPP) that provide service capabilities that areexposed to application providers, for example, via open mobilealliance-application programming interface (OMA-API(s)), may benefitfrom application control interworking in a network. Further, anapplication programming interface (API) and the 3GPP system can acttogether to expose 3GPP service capabilities.

Description of the Related Art

Architecture Enhancements for Service Capability is a new item beingworked on by 3GPP. For example, 3GPP has been aiming at normativespecifications within 3GPP Rel-13. A number of measures can be appliedeither separately, or in various combinations to define and optimize thenetwork architecture and required/related control procedures andinteractions between network entities for introducing service capabilityexposure and enablement support in 3GPP specifications.

When the service capability exposure is applied to a mobile network thatalso supports application detection and control (ADC), the network alsoapplies, as per current specifications, the ADC to the traffic betweenthe user equipment (UE) and the application server (AS). This isdescribed, for example, in 3GPP Technical Specification 23.203 and29.212. In case of some servers and/or applications, this may causeredundant activities with parallel processing for the same purpose,extra message exchanges and bearer establishments or modifications thatshould be rectified as soon as the wanted information is available fromthe application server. This can be prevented with a simpleconfiguration measure that excludes the servers from the list ofpossibly detectable applications by a traffic detection function (TDF).For example, one configuration measure may be to exclude the InternetProtocol (IP) addresses of the servers from the list of possiblydetectable applications by TDF.

In order to optimize the network architecture and the policy and/orcharging control of applications, it may be desirable in some cases toapply ADC to the traffic between a UE and an application server. Thus,for such cases, the configuration measure can close doors foroptimization of the network architecture and for the optimization ofpolicy and charging control procedures of different application serversand/or applications.

SUMMARY

According to certain embodiments, a method can include receivingparameters of capabilities relating to an application server at a policyand charging rules function. The method can also include creatingapplication detection and control rules based on the parametersreceived.

According to certain embodiments, a method can include receiving atleast one of capabilities, application related capabilities andparameters for different applications from an application server. Themethod can also include providing the at least one of capabilities,application related capabilities and parameters for differentapplications to a policy and charging rules function in response to arequest from the policy and charging rules function for the capabilitiesor parameters.

According to certain embodiments, a method can include maintaining atleast one of a plurality of indicators indicated to a service capabilityfunction. The method can also include indicating, from an applicationserver to the service capability function, the plurality of indicatorsrelated to the application server.

An apparatus, according to certain embodiments, can include at least oneprocessor and at least one memory including computer program code. Theat least one memory and the computer program code can be configured to,with the at least one processor, cause the apparatus at least to receiveparameters of capabilities relating to an application server at a policyand charging rules function. The at least one memory and the computerprogram code can also be configured to, with the at least one processor,cause the apparatus at least to create application detection and controlrules based on the parameters received.

An apparatus, in certain embodiments, can include means for receivingparameters of capabilities relating to an application server at a policyand charging rules function. The apparatus can also include means forcreating application detection and control rules based on the parametersreceived.

An apparatus, according to certain embodiments, can include at least oneprocessor and at least one memory including computer program code. Theat least one memory and the computer program code can be configured to,with the at least one processor, cause the apparatus at least to receiveat least one of capabilities, application related capabilities andparameters for different applications from an application server. The atleast one memory and the computer program code can also be configuredto, with the at least one processor, cause the apparatus at least toprovide the at least one of capabilities, application relatedcapabilities and parameters for different applications to a policy andcharging rules function in response to a request from the policy andcharging rules function for the capabilities or parameters.

An apparatus, in certain embodiments, can include means for receiving atleast one of capabilities, application related capabilities andparameters for different applications from an application server. Theapparatus can also include means for providing the at least one ofcapabilities, application related capabilities and parameters fordifferent applications to a policy and charging rules function inresponse to a request from the policy and charging rules function forthe capabilities or parameters.

An apparatus, according to certain embodiments, can include at least oneprocessor and at least one memory including computer program code. Theat least one memory and the computer program code can be configured to,with the at least one processor, cause the apparatus at least tomaintain at least one of a plurality of indicators indicated to aservice capability function. The at least one memory and the computerprogram code can also be configured to, with the at least one processor,cause the apparatus at least to indicate, from an application server tothe service capability function, the plurality of indicators related tothe application server.

An apparatus, in certain embodiments, can include means for maintainingat least one of a plurality of indicators indicated to a servicecapability function. The apparatus can also include means forindicating, from an application server to the service capabilityfunction, the plurality of indicators related to the application server.

BRIEF DESCRIPTION OF THE DRAWINGS

For proper understanding of the invention, reference should be made tothe accompanying drawings, wherein:

FIG. 1 illustrates a basic, simplified architecture example, when aproposal is applied to a 3GPP environment, according to certainembodiments.

FIG. 2 illustrates a signaling scenario wherein an application serverand network exchange information and a user equipment attaches to thenetwork, according to certain embodiments.

FIG. 3 illustrates a signaling scenario wherein a traffic detectionfunction detects an application and related information is available ata service capability function, according to certain embodiments.

FIG. 4 illustrates a signaling scenario wherein the traffic detectionfunction detects an application, related session information isavailable at an application server AS-x and a control interface existsbetween AS-x and a policy and/or charging enforcement function,according to certain embodiments.

FIG. 5 illustrates a system according to certain embodiments.

FIG. 6 illustrates a method according to certain embodiments.

FIG. 7 illustrates another method according to certain embodiments.

FIG. 8 illustrates yet another method according to certain embodiments.

DETAILED DESCRIPTION

Certain embodiments may provide a simplified architecture, when serviceexposure is applied to a 3GPP network. An example of such architectureis shown in FIG. 1, which is based on 3GPP. According to FIG. 1, serviceexposure can be based on information exchange between an applicationserver (AS-x) through an API and a service capability function (SCF)/APIgateway function.

FIG. 1 also shows a UE in communication with an access network, which isin communication with a packet data network gateway (P-GW). The P-GW mayinclude a policy and charging enforcement function (PCEF). The P-GW isin communication with a TDF. The P-GW is also in communication with apolicy and charging rules function (PCRF) via a Gx interface. The TDF isalso in communication with the PCRF via an Sd interface. The TDF isfurther in communication with AS-x and AS-y. FIG. 1 further shows thatthe PCRF is in communication with the SCF/API gateway function via aninterface Xx defined as, for example, an Rx interface.

According to certain embodiments, various measures that can be appliedseparately or in various combinations can be obtained in light of thesimplified architecture shown in FIG. 1. For example, the AS-x mayindicate, in addition to its own identity, such as for example, an IPaddress, one or more issues to the SCF/API gateway (GW) function. Forexample, one issue may include whether or not the AS-x supports acontrol interface to provide session information to the network, such asfor example, to PCRF, when a user session is established between a UEand the AS-x. This determination can be used by the network (PCRF, TDF),for example, for deciding whether the ADC should be applied toapplications running on the AS-x.

Another issue may include adding granularity to the step above in thecase where the AS-x supports provisioning of session information. Forexample, the addition of granularity may involve per application or perservice, whether or not session information is provided for theapplication, when it is activated. Activation may occur, for example,when an application session is established between the UE and AS-x. Thisissue can be used by the network, such as PCRF, for example, fordeciding on to which applications the ADC should be applied, and towhich applications the ADC should not be applied.

A further issue may include an indication of the availability ofapplication specific policy information and the information itself,including, for example, acceptable quality of service (QoS) or QoSranges, charging control. This indication may be used by the network,such as by PCRF, to provide initial ADC and policy and/or chargingcontrol (PCC) rules accordingly. As discussed in more detail below, anexample of such an implementation is shown in FIG. 2, steps 7-13. Thisindication may also be used by the network without further sessioninformation provisioning when the network (ADC) detects thecorresponding service start between the UE and AS-x, as shown in FIG. 3,steps 1-8, which is further described in detail below.

According to certain embodiments, AS-x may dynamically update theinformation to keep the SCF/network abreast of the latest status, andaccordingly the SCF/network may dynamically update the status of theexposed services.

Further details of the required behavior of the related networkfunctions (PCRF, TDF, SCF and AS-x) in various cases/embodiments aredescribed in more detail below with reference to FIGS. 2, 3 and 4.

Even though a standalone TDF can be used in these examples/embodiments,the same procedures and measures may also apply, when TDF is integratedin P-GW, such as, for example, being collocated with PCEF, in P-GW. Inthis case message exchanges between PCRF and P-GW replace messageexchanges between PCRF and TDF, as discussed below.

FIG. 2 illustrates an implementation of a signaling scenario where theAS and network (SCF) exchange information and a UE attaches to thenetwork. As shown in FIG. 2, at step 1, SCF and AS-x exchangeinformation. SCF exposes network services to AS-x. AS-x may indicate itscapabilities and application related capabilities and parameters fordifferent applications including the various issues indicated to theSCF/API GW described above.

At step 2, the UE can attach to the network via an attach requestincluding parameters. At step 3, as a consequence of the UE attaching tothe network, P-GW may obtain a request message for setting up a defaultsession/context for the UE. At step 4, P-GW can request authorizationand PCC rules for the session context from PCRF. Next, at step 5, PCRFmay request the subscription profile/subscription parameters of the userfrom a subscription profile repository/user data repository (SPR/UDR).At step 6, the SPR/UDR may send the subscription profile/subscriptionparameters in its response to PCRF. The profile/parameters maycontain/identify applications/services allowed for the user.

The PCRF may deduce, at step 7, for example, by configuration or from aprior setup of a control protocol with SCF or from the subscriptionprofile/parameters that a query to the SCF is to be made. At step 8, thePCRF can send a request to SCF to get possible capability informationrelated to AS-x and other application servers, and/or informationrelated to applications/services offered by the application servers. Theparameters in the request may identify applications/services allowed forthe user. At step 9, SCF can send a response to PCRF. The response maycontain capabilities of identified application servers and applicationrelated capabilities and parameters for different applicationsincluding, for example, the issues indicated to the SCF/API GW describedabove.

At step 10, the PCRF can use the information received from SCF and fromSPR/UDR for creating ADC rules for TDF and/or PCC rules for P-GW thatmay include a policy and charging enforcement function (PCEF). PCRF mayespecially use the application server related information and/orapplication related information for deducing from/deciding on which ofthe detected applications should make the TDF send a report to PCRF andwhich should not.

At step 11, PCRF may send a request message to TDF. The message maycontain ADC rules. At step 12, TDF can send a response to PCRF. PCRF cansend, at step 13, a response message to P-GW. The message may containPCC Rules. The PCC rules may contain rules for policy enforcement forPCEF and/or rules for application detection, if TDF is integrated withPCEF in P-GW, in which case steps 11 and 12 can be omitted.

At step 14, P-GW can send a response to message 3. Finally, at step 15,the UE can get an acknowledgement for the attach request/message 2.

FIG. 3 illustrates another implementation of a signaling scenario whereTDF can detect an application to have related information available atthe SCF, according to certain embodiments. At step A, SCF and AS-x mayexchange information to update the statuses. Here, SCF may update thestatus of network services to AS-x. AS-x may indicate its capabilitiesand application related capabilities and parameters for differentapplications including the issues indicated to the SCF/API GW describedabove.

At step 1, TDF can detect an application related to AS-x and indicatedearlier (by SCF) to have related information, such as, for example,related to QoS, charging, available at the SCF. At step 2, TDF can senda message to PCRF to indicate the detection of an application. Inaddition to the regular application related information, the parametersmay, but do not have to, indicate to PCRF a need to request furtherinformation from SCF.

The PCRF can, at step 3, deduce, for example, from the AS-x/application,related information received earlier from SCF, or from an indicationsent by TDF in step 2 or by configuration that a query to the SCF shallbe made to get application server/AS-x or application relatedinformation. At step 4, PCRF can send a request to SCF. The parametersin the request may identify the detected application and/or theapplication server, for example, through an IP address. At step 5, SCFcan send a response to PCRF. The response may contain applicationrelated capabilities for the detected application and/or capabilities ofthe identified application server, such as, for example, the issuesindicated to the SCF/API GW described above.

At step 6, PCRF can create PCC and/or ADC rules based on the applicationrelated information/parameters and/or the application server AS-xrelated information/parameters received from SCF. At step 7, PCRF cansend a response message to TDF. The message may contain ADC rules. Atstep 8, PCRF may send a request message to P-GW. The message may containPCC rules. The PCC rules may contain rules for policy enforcement forPCEF and/or rules for application detection, if TDF is integrated withPCEF in P-GW, in which case step 2 originates from P-GW, step 7terminates at P-GW and steps 8 and 9 can be omitted. Finally, at step 9,P-GW can send a response to message 8 to PCRF.

FIG. 4 illustrates another implementation of a signaling scenario whereTDF can detect an application to have related session informationavailable at the application server AS-x and that a control interfaceexists between AS-x and PCRF. At step 1, a UE and an application serverAS-x can exchange an IP packet/IP packets on the traffic channel/userplane. At step 2, TDF can detect an application related to theapplication server AS-x and indicated earlier (by SCF) that AS-x willprovide related session information upon session establishment.Consequently, TDF can refrain from contacting PCRF.

At step 3, AS-x can set up an application session with UE in step 1above, and deduce related session information/parameters. At step 4,AS-x can send session information/parameters in a request message toPCRF. At step 5, PCRF can send a response to AS-x. PCRF can, at step 6,create PCC and/or ADC rules based on the session information/parametersreceived from AS-x.

At step 7, PCRF can send a request message to P-GW. The message maycontain PCC rules. The PCC rules may contain rules for policyenforcement for PCEF and/or rules for application detection, if TDF isintegrated with PCEF in P-GW, in which case steps 9 and 10 can beomitted. At step 8, P-GW can send a response to PCRF. At step 9, PCRFmay send a request message to TDF. The message may contain ADC rules.Finally, at step 10, TDF can send a response to message 9 to PCRF.

Certain embodiments may have various benefits and/or advantages. Forexample, in certain embodiments, crucial elements may include PCRF,PCEF/TDF and the to-be-defined (under work in 3GPP) SCF/API GW.According to certain embodiments, these entities can adapt to thecapabilities of external application servers to get the most of theavailable services and applications. This suggests a number of measuresthat can be applied either separately or in various combinations.

FIG. 5 illustrates a system according to certain embodiments of theinvention. In one embodiment, a system may include multiple devices,such as, for example, at least one first network element, such as, forexample, PCRF 510, at least one second network element, such as, forexample, SCF 520, and at least one third network element, such as, forexample, application server 530.

Each of these devices may include at least one processor, respectivelyindicated as 514, 524, and 534. At least one memory can be provided ineach device, and indicated as 515, 525, and 535, respectively. Thememory may include computer program instructions or computer codecontained therein. The processors 514, 524, and 534 and memories 515,525, and 535, or a subset thereof, can be configured to provide meanscorresponding to the various blocks of FIG. 5.

Even though described as separate devices in FIG. 1, some of thesedevices, such as, for example, PCRF and SCF, may be integrated asfunctionalities in a single device.

As shown in FIG. 5, transceivers 516, 526, and 536 can be provided, andeach device may also include an antenna, respectively illustrated as517, 527, and 537. Transceivers 516, 526, and 536 can each,independently, be a transmitter, a receiver, or both a transmitter and areceiver, or a unit or device that is configured both for transmissionand reception.

Processors 514, 524, and 534 can be embodied by any computational ordata processing device, such as a central processing unit (CPU),application specific integrated circuit (ASIC), or comparable device.The processor can be implemented as a single controller, or a pluralityof controllers or processors.

Memories 515, 525, and 535 can be any suitable storage device, such as anon-transitory computer-readable medium. A hard disk drive (HDD), randomaccess memory (RAM), flash memory, or other suitable memory can be used.The memories can be combined on a single integrated circuit as theprocessor, or may be separate from the one or more processors.Furthermore, the computer program instructions stored in the memory andwhich may be processed by the processors can be any suitable form ofcomputer program code, for example, a compiled or interpreted computerprogram written in any suitable programming language.

The memory and the computer program instructions can be configured, withthe processor for the particular device, to cause a hardware apparatussuch as PCRF 510, SCF 520, and application server 530, to perform any ofthe processes described herein (see, for example, FIGS. 2-4 and 6-8).Therefore, in certain embodiments, a non-transitory computer-readablemedium can be encoded with computer instructions that, when executed inhardware, perform a process such as one of the processes describedherein. Alternatively, certain embodiments of the invention can beperformed entirely in hardware.

Furthermore, although FIG. 5 illustrates a system including a PCRF, SCF,and application server, embodiments of the invention may be applicableto other configurations, and configurations involving additionalelements. For example, not shown, additional core network elements maybe present, as illustrated in FIGS. 1-4.

FIG. 6 illustrates a method according to certain embodiments. As shownin FIG. 6, a method can include, at step 610, receiving parameters ofcapabilities relating to a first network element, such as, for example,an application server, at a second network element, such as, forexample, a policy and charging rules function. The method can alsoinclude, at step 620, creating application detection and control rules.The application detection and control rules can be based on theparameters received.

The method can further include, at step 630, creating policy and/orcharging control rules. The policy and/or charging control rules can becreated based on the parameters received relating to the first networkelement. The method can also include, at step 640, requestingsubscription profile and/or subscription parameters of a user. Thesubscription profile and/or subscription parameters can includeapplications and/or services that are allowed for the user.

The method can further include, at step 650, determining that a query toa third network element, such as, for example, a service capabilityfunction, should be made based on a configuration or a prior setup of acontrol protocol with the third network element, or from thesubscription profile and/or subscription parameters of the user. Themethod can also include, at step 660, receiving a message from a fourthnetwork element, such as, for example, a traffic detection function, atthe second network element. The message can indicate detection of atleast one of a plurality of applications. The method can also include,at step 670, determining that a query to the third network elementshould be made based on application related information or from themessage sent by the fourth network element.

FIG. 7 illustrates another method according to certain embodiments. Asshown in FIG. 7, a method can include, at step 710, receivingcapabilities and application related capabilities and parameters fordifferent applications from a first network element, such as, forexample, an application server. The method can also include, at step720, providing the capabilities and application related capabilities andparameters for different applications to a second network element, suchas, for example, a policy and charging rules function. The capabilitiesand application related capabilities and parameters can be provided inresponse to a request from the policy and charging rules function forthe capabilities and parameters.

The method can further include, at step 730, dynamically updating thestatus of network services to the first network element based on updatedindicators related to the first network element received from the firstnetwork element. The method can also or alternatively include, at step740, receiving updates from the application server relating to servicesthat the application server supports. The updates may indicate, forexample, QoS and charging control related parameters related to theservices that the application server supports.

FIG. 8 illustrates yet another method according to certain embodiments.As shown in FIG. 8, a method can include, at step 810, maintaining atleast one of a plurality of indicators indicated to a first networkelement, such as, for example, a service capability function. The methodcan also include, at step 820, indicating the plurality of indicatorsrelated to a second network element, such as, for example, anapplication server. The plurality of indicators can be indicated fromthe second network element to the first network element.

The method can further include, at step 830, indicating the secondnetwork element's own identity to the first network element. The secondnetwork element's own identity can be indicated to the first networkelement by the second network element. The method can also oralternatively include, at step 840, providing indications related toapplications supported by the second network element to the firstnetwork element. The method can further include, at step 850, sendingupdates from the application server to the service capability functionrelating to services that the application server provides.

One having ordinary skill in the art will readily understand that theinvention as discussed above may be practiced with steps in a differentorder, and/or with hardware elements in configurations which aredifferent than those which are disclosed. Therefore, although theinvention has been described based upon these preferred embodiments, itwould be apparent to those of skill in the art that certainmodifications, variations, and alternative constructions would beapparent, while remaining within the spirit and scope of the invention.In order to determine the metes and bounds of the invention, therefore,reference should be made to the appended claims.

GLOSSARY

-   3GPP Third Generation Partnership Project-   ADC Application Detection and Control-   API Application Programming Interface-   AS Application Server-   ASIC Application Specific Integrated Circuit-   CPU Central Processing Unit-   GW Gateway-   HDD Hard Disk Drive-   IP Internet Protocol-   IP-CAN IP Connectivity Access Network-   OMA Open Mobile Alliance-   PCC Policy and/or Charging Control-   PCEF Policy and Charging Enforcement Function-   PCRF Policy and Charging Rules Function-   P-GW Packet Data Network Gateway-   QoS Quality of Service-   RAM Random Access Memory-   SCF Service Capability Function-   SPR Subscription Profile Repository-   TDF Traffic Detection Function-   UDR User Data Repository-   UE User Equipment

1. A method, comprising: receiving parameters of capabilities relatingto an application server at a policy and charging rules function; andcreating application detection and control rules based on the parametersreceived.
 2. (canceled)
 3. The method of claim 1, wherein the parameterscomprise at least one of capabilities of identified application servers,application related capabilities and parameters for a plurality ofdifferent applications.
 4. The method of claim 1, further comprising:requesting subscription profile and/or subscription parameters of auser, wherein the subscription profile and/or subscription parameterscomprise applications and/or services allowed for the user.
 5. Themethod of claim 1, further comprising: determining that a query to aservice capability function should be made based on a configuration or aprior setup of a control protocol with the service capability function,or from the subscription profile and/or subscription parameters of theuser.
 6. The method of claim 1, further comprising: receiving a messagefrom a traffic detection function at the policy and charging rulesfunction, wherein the message indicates detection of at least one of theplurality of applications.
 7. The method of claim 6, further comprising:determining that a query to a service capability function should be madebased on application related information or on the message sent by thetraffic detection function.
 8. (canceled)
 9. A method, comprising:receiving, at a service capability function, at least one ofcapabilities, application related capabilities and parameters fordifferent applications from an application server; and providing the atleast one of capabilities, application related capabilities andparameters for different applications to a policy and charging rulesfunction in response to a request from the policy and charging rulesfunction for the capabilities or parameters.
 10. The method of claim 9,wherein the request is a request to obtain information related toapplications/services offered by the application server, wherein therequest identifies applications/services allowed for a user, and whereinthe response further comprises the information related toapplications/services offered by the application server.
 11. The methodof claim 9, wherein the request identifies a detected application and/orthe application server, and wherein the response comprises applicationrelated capabilities for the detected application and/or capabilities ofthe identified application server.
 12. (canceled)
 13. (canceled)
 14. Amethod, comprising: maintaining at least one of a plurality ofindicators indicated to a service capability function; and indicating,from an application server to the service capability function, theplurality of indicators related to the application server.
 15. Themethod of claim 14, further comprising: providing indications related toapplications supported by the application server to the servicecapability function.
 16. (canceled)
 17. (canceled)
 18. The method ofclaim 14, further comprising: indicating, by the application server, theapplication server's own identity to the service capability function.19. The method of claim 14, wherein at least one of the plurality ofindicators indicates at least one of: whether or not the applicationserver supports a control interface to provide session information to anetwork when a user session is established between a user equipment andthe application server; whether or not session information is providedfor application when an application session is established between auser equipment the application server; and availability of applicationspecific policy information.
 20. (canceled)
 21. (canceled)
 22. Anapparatus comprising: at least one processor; and at least one memoryincluding computer program code, wherein the at least one memory and thecomputer program code are configured to, with the at least oneprocessor, cause the apparatus at least to receive parameters ofcapabilities relating to an application server at a policy and chargingrules function; and create application detection and control rules basedon the parameters received.
 23. (canceled)
 24. The apparatus of claim22, wherein the parameters comprise at least one of capabilities ofidentified application servers, application related capabilities andparameters for a plurality of different applications.
 25. The apparatusof claim 22, wherein the at least one memory and the computer programcode are configured to, with the at least one processor, cause theapparatus at least to request subscription profile and/or subscriptionparameters of a user, wherein the subscription profile and/orsubscription parameters comprise applications and/or services allowedfor the user.
 26. The apparatus of claim 22, wherein the at least onememory and the computer program code are configured to, with the atleast one processor, cause the apparatus at least to determine that aquery to a service capability function should be made based on aconfiguration or a prior setup of a control protocol with the servicecapability function, or from the subscription profile and/orsubscription parameters of the user.
 27. The apparatus of claim 22,wherein the at least one memory and the computer program code areconfigured to, with the at least one processor, cause the apparatus atleast to receive a message from a traffic detection function at thepolicy and charging rules function, wherein the message indicatesdetection of at least one of the plurality of applications.
 28. Theapparatus of claim 27, wherein the at least one memory and the computerprogram code are configured to, with the at least one processor, causethe apparatus at least to determine that a query to the servicecapability function should be made based on application relatedinformation or on the message sent by the traffic detection function.29.-37. (canceled)
 38. An apparatus, comprising: at least one processor;and at least one memory including computer program code, wherein the atleast one memory and the computer program code are configured to, withthe at least one processor, cause the apparatus at least to receive atleast one of capabilities, application related capabilities andparameters for different applications from an application server; andprovide the at least one of capabilities, application relatedcapabilities and parameters for different applications to a policy andcharging rules function in response to a request from the policy andcharging rules function for the capabilities or parameters.
 39. Theapparatus of claim 38, wherein the request is a request to obtaininformation related to applications/services offered by the applicationserver, wherein the request identifies applications/services allowed fora user, and wherein the response further comprises the informationrelated to applications/services offered by the application server. 40.The apparatus of claim 38, wherein the request identifies a detectedapplication and/or the application server, and wherein the responsecomprises application related capabilities for the detected applicationand/or capabilities of the identified application server. 41.-47.(canceled)
 48. An apparatus, comprising: at least one processor; and atleast one memory including computer program code, wherein the at leastone memory and the computer program code are configured to, with the atleast one processor, cause the apparatus at least to maintain at leastone of a plurality of indicators indicated to a service capabilityfunction; and indicate, from an application server to the servicecapability function, the plurality of indicators related to theapplication server.
 49. The apparatus of claim 48, wherein the at leastone memory and the computer program code are configured to, with the atleast one processor, cause the apparatus at least to provide indicationsrelated to applications supported by the application server to theservice capability function.
 50. (canceled)
 51. (canceled)
 52. Theapparatus of claim 48, wherein the at least one memory and the computerprogram code are configured to, with the at least one processor, causethe apparatus at least to indicate, by the application server, theapplication server's own identity to the service capability function.53. The apparatus of claim 48, wherein at least one of the plurality ofindicators indicates at least one of: whether or not the applicationserver supports a control interface to provide session information to anetwork when a user session is established between a user equipment andthe application server; whether or not session information is providedfor application when an application session is established between auser equipment the application server; and availability of applicationspecific policy information. 54.-69. (canceled)